Codecov Report

❌ Patch coverage is 43.89535% with 193 lines in your changes missing coverage. Please review.
✅ Project coverage is 18.47%. Comparing base (71098f6) to head (a46917a).
⚠️ Report is 259 commits behind head on main.

@@            Coverage Diff             @@
##            main     #206       +/-   ##
==========================================
+ Coverage   0.00%   18.47%   +18.47%     
==========================================
  Files          4       35       +31     
  Lines         26     1402     +1376     
  Branches       0      239      +239     
==========================================
+ Hits           0      259      +259     
- Misses        26     1114     +1088     
- Partials       0       29       +29     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@vrubezhny, @azatsarynnyy: please review. To test it:

1. EXEC: launch gateway plugin, get to the wizard page where you provide cluster & token
2. EXEC: change kube config (add/remove/change cluster/token, etc.) or any file listed in KUBECONFIG env variable using an (external) tool while keeping wizard opened.
3. ASSERT: selected cluster/token should reflect the new values
4. ASSERT: "Next"-button should get enabled/disabled when you select a cluster and provide (or remove) a token
   Thanks!

ps. KUBECONFIG env variable looks as follows (on MacOS, set it in ~/.zprofile):

export KUBECONFIG=${HOME}/.kube/config:${HOME}/.kube/minikube.yaml

Token doesn't get renewed from Kube config when it's changed while you were at Select running DevWorkspace wizard page and press Back button: you'll still see an old token value.

Steps to reproduce:

• Open Connect to Dev Spaces wizard - see some cluster selected together with the related token value (which is up-to-date)
• Press Check connection ans continue to go to the Select running DevWorkspace wizard page.
• While on the page, request the new token, copy-paste its value to your Kube config and save it.
• Press Back on the Select running DevWorkspace wizard page to go back to the cluster selection wizard page
• Fail: Connecting to OpenShift API server wizard page still shows the OLD token value for the selected server

@vrubezhny: thx for findining this! Fixed it. I now start watching kube config files when the wizard page is shown and stop when it is hidden.
Please re-review/test :)

added a test and printing of the full stacktrace if a test fails (suggested by @vrubezhny)